Configure Resilient Hashing on Tenant VRF

As a load-balancing method, resilient hashing helps to lessen the possibility that a destination path is remapped when a LAG (Link Aggregation Group) link fails.

About this task

When you create or update a tenant VRF, you can enable ECMP resilient hashing and you can configure the maximum number of resilient hashing paths allowed (8, 16, or 64 paths). Resilient hashing is disabled by default. The default number of allowed paths is the same as the default value for the SLX devices.

Procedure

To enable resilient hashing when you create a tenant VRF, use the efa tenant vrf create command with the --rh-ecmp-enable and --rh-max-path parameters, and set the maximum number of allowed paths. For example,
```
# efa tenant vrf create --name <vrf-name> --tenant <tenant-name> 
--rh-ecmp-enable=true/false --rh-max-path <8 | 16 | 64 | 128>
```
To enable resilient hashing on an existing tenant VRF, use the efa tenant vrf update command with the --rh-ecmp-enable and --rh-max-path parameters, and set the maximum number of allowed paths. For example,
```
# efa tenant vrf update --name <vrf-name> --tenant <tenant-name> 
--operation <rh-max-path-add | rh-max-path-delete | rh-ecmp-update> 
--rh-ecmp-enable=true/false --rh-max-path <8 | 16 | 64 | 128>
```
Note
- The --max-path and --rh-max-path parameters can co-exist.
- You cannot choose the specific devices on which to configure resilient hashing. Configuration applies to all SLX devices in the tenant VRF.
- For more information about the commands, including usage examples, see the ExtremeCloud Orchestrator Command Reference, 3.6.0 .